Skip to content

Populate Run Configuration from the build's declarations - #35

Open
ChrisonSimtian wants to merge 2 commits into
developfrom
run-config-from-declarations
Open

ChrisonSimtian wants to merge 2 commits into
developfrom
run-config-from-declarations

Conversation

@ChrisonSimtian

Copy link
Copy Markdown
Contributor

Closes #1. Closes #32.

Run Configuration now lists what the build declares, and offers the verbosity levels the build supports.

  • Declared [Parameter] members appear as rows, with a drop-down for enum values and the description as a tooltip.
  • Declared [Secret] members read "not set" until a value is stored. Values still go to SecretStorage and are passed as environment variables.
  • A Verbosity drop-down is filled from the build's schema, so Information shows only on 10.5+. The choice is passed as --verbosity <level>.
  • An empty value clears a parameter, so --name is never passed.
  • Free-form rows still work for anything the build does not declare.

Source of the declarations

  • parameters[] from build-graph.json when present (Fallout#499, not shipped yet).
  • Otherwise .fallout/build.schema.json, which the build writes on every run. A secret is the member whose default carries the framework's "Secrets must be entered via" placeholder, the same marker fallout secrets reads.
  • Neither file: the view stays free-form, as today.

Start reading at loadDeclarations in src/model.ts.

Verified

  • tsc is clean.
  • Parsed the real schemas of the Fallout repo (finds NuGetApiKey and CodecovToken as secrets, the Configuration enum, and Information) and of this repo (4 levels, no Information).
  • Rendered the webview in jsdom with those declarations. Checked the "not set" state, clearing a value, and the verbosity and secret messages.
  • Not tried in the Extension Development Host. Please F5 once before merge.

🤖 Generated with Claude Code

https://claude.ai/code/session_01G6hKb8BB3N8iss2KABGq6s

List declared parameters and secrets in the Run Configuration view, read from build-graph.json when it carries parameters[] and from build.schema.json otherwise. Add a verbosity drop-down fed from the same schema, so new levels such as Information appear without a hard-coded list.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G6hKb8BB3N8iss2KABGq6s
@ChrisonSimtian ChrisonSimtian added this to the v10.5 milestone Nov 15, 2026
@ChrisonSimtian ChrisonSimtian added the enhancement New feature or request label Nov 15, 2026
@coderabbitai

coderabbitai Bot commented Nov 15, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Offer the Information verbosity in Run Configuration Run Configuration: populate parameters & secrets from the build's declarations

1 participant